Email-based transactions for e-commerce

ABSTRACT

An electronic commerce (e-commerce) system may send advertisement emails to customers that are registered with the e-commerce system. The advertisement emails may include mailto hyperlinks. Each mailto hyperlink may be associated with a product that is being offered for sale, and each mailto hyperlink describes an email message that may be generated when that hyperlink is selected. When a mailto hyperlink is selected, the generated email message may include one or more parameters related to the product associated with the hyperlink, such as an identifier of the product. The generated email message may then be transmitted to the e-commerce system. The e-commerce system may receive the message and, based on the parameters in the received message, execute a transaction to purchase the identified product on behalf of the customer.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.17/526,363 filed Nov. 15, 2021, which is a continuation of U.S. patentapplication Ser. No. 17/035,010 filed Sep. 28, 2020, now U.S. Pat. No.11,188,939 issued on Nov. 30, 2021, which is a continuation of Ser. No.16/057,641, filed Aug. 7, 2018, now U.S. Pat. No. 10,789,618 issued onSep. 29, 2020, which is a continuation of U.S. patent application Ser.No. 14/875,156 filed Oct. 5, 2015, now U.S. Pat. No. 10,049,385 issuedon Aug. 14, 2018, which is a continuation of U.S. patent applicationSer. No. 14/324,807 filed on Jul. 7, 2014, now U.S. Pat. No. 9,152,980issued on Oct. 6, 2015, which is a continuation of U.S. patentapplication Ser. No. 13/074,222, filed on Mar. 29, 2011, now U.S. Pat.No. 8,775,263 issued on Jul. 8, 2014, which are hereby incorporated byreference herein.

This application is related to U.S. patent application Ser. No.14/738,098, filed Jun. 12, 2015 entitled “EMAIL-BASED DONATIONS”, whichis a continuation of U.S. patent application Ser. No. 13/074,235entitled “SYSTEM AND METHOD FOR EMAIL-BASED DONATIONS,” filed on Mar.29, 2011, which issued as U.S. Pat. No. 9,058,591, on Jun. 16, 2015,which are hereby incorporated by reference herein.

BACKGROUND

According to many current approaches to electronic commerce(e-commerce), a customer may register with a vendor (such as an onlineretailer) to receive emails that provide information about products thatare offered for sale by the vendor. The emails may include hyperlinksthat direct the user to web pages on the vendor's web site. At the website, the customer may obtain additional information about and/orpurchase the products described in the emails.

If the customer originally received an email in a dedicated emailapplication such as Microsoft Outlook, a different application (such asa web browser) must be used in order to view the web pages on thevendor's web site. Further, to purchase a product from the vendor's website, customers are frequently required to enter payment informationsuch as credit card information. Due to this switch to a differentapplication and the entry of credit card information, the process ofpurchasing a product from the vendor becomes inconvenient andtime-consuming. Further, when non-profit organizations conduct emailmarketing campaigns, the donation process may be similar to thatdescribed above, and may be fraught with similar problems. Therefore,more streamlined and convenient approaches to e-commerce would beadvantageous.

SUMMARY

A method for use in an e-commerce system may include a database storinginformation that includes an identifier of a customer, an email addressof the customer, and an identifier of a product offered by a vendor. Themethod may further include at least one processor generating anadvertising email message. The advertising email message may beaddressed to the email address of the customer, and may include a mailtohyperlink. The mailto hyperlink may include a destination address fieldthat indicates an email address of the e-commerce system, and a bodyfield that indicates an email body that includes the identifier of thecustomer and the identifier of the product. The method may furtherinclude a network interface transmitting the advertising email message,and the network interface receiving an order email message. The orderemail message may indicate an order by the customer for the product. Theorder email message may be responsive to the advertising email message,and may be addressed to the email address of the e-commerce system. Thebody of the order email message may include the identifier of thecustomer and the identifier of the product. The at least one processorand the network interface may perform an order execution procedure basedon the order email message, wherein the order execution procedureincludes purchasing the product for the customer.

An e-commerce system may include a database, at least one processor, anda network interface. The database may be configured to store informationthat includes an identifier of a customer, an email address of thecustomer, and an identifier of a product offered by a vendor. The atleast one processor may be configured to generate an advertising emailmessage that is addressed to the email address of the customer, andincludes a mailto hyperlink. The mailto hyperlink may include adestination address field that indicates an email address of thee-commerce system, and a body field that indicates an email body thatincludes the identifier of the customer and the identifier of theproduct. The network interface may be configured to transmit theadvertising email message and to receive an order email message. Theorder email message may indicate an order by the customer for theproduct. The order email message may be responsive to the advertisingemail message, and may be addressed to the email address of thee-commerce system. The body of the order email message may include theidentifier of the customer and the identifier of the product. The atleast one processor and the network interface may be further configuredto perform an order execution procedure based on the order emailmessage, wherein the order execution procedure includes purchasing theproduct for the customer.

A computer-readable storage medium having processor-executableinstructions stored thereon which, when executed by at least oneprocessor in an e-commerce system, will cause the at least one processorto perform a method. The method may include storing information thatincludes an identifier of a customer, an email address of the customer,and an identifier of a product offered by a vendor. The method mayfurther include generating an advertising email message, wherein theadvertising email message is addressed to the email address of thecustomer, and includes a mailto hyperlink. The mailto hyperlink mayinclude a destination address field that indicates an email address ofthe e-commerce system and a body field that indicates an email body thatincludes the identifier of the customer and the identifier of theproduct. The method may further include transmitting, via a networkinterface, the advertising email message. The method may further includereceiving, via the network interface, an order email message. The orderemail message may be responsive to the advertising email message, andmay be addressed to the email address of the e-commerce system. The bodyof the order email message may include the identifier of the customerand the identifier of the product. The method may further includeperforming an order execution procedure based on the order emailmessage, wherein the order execution procedure includes purchasing theproduct for the customer.

BRIEF DESCRIPTION OF THE DRAWINGS

A more detailed understanding may be had from the following description,given by way of example in conjunction with the accompanying drawingswherein:

FIG. 1 shows a logical architecture for engaging in electronic commerceusing email;

FIGS. 2A-2B show a method for engaging in electronic commerce usingemail;

FIG. 3 shows an example advertisement email message that solicits thepurchase of goods from a vendor;

FIG. 4 shows an email message for placing an order;

FIG. 5 shows an advertisement email message that solicits a donation toa non-profit organization;

FIG. 6 shows an email message for ordering a donation to a non-profitorganization;

FIG. 7 shows a first order confirmation email message;

FIG. 8 shows an example order confirmation method;

FIG. 9 shows a second order confirmation email message;

FIG. 10 shows an email message that may be used to confirm an order;

FIG. 11 shows an email message that may be used to cancel an order;

FIG. 12 shows an example order execution method; and

FIG. 13 shows an example system that may be used to implement featuresdescribed herein with reference to FIGS. 1-12 .

DETAILED DESCRIPTION

FIG. 1 shows an example logical architecture 114 for email-basede-commerce. The example architecture 114 may include a customer clientdevice 120, an e-commerce system 100, a payment processing system 136, avendor order fulfillment system 138, and a vendor client device 130. Thee-commerce system 100 may include an account management module 102, adatabase module 104, an e-commerce database 106, an order executionmodule 108, a message processing module 110, and an email interfacemodule 112. As will be described in further detail below, the e-commercesystem 100 and customer client device 120 may exchange email messages toinitiate and manage transactions such as donations to non-profitorganizations and/or the purchase of goods. Also as will be described infurther detail below, the e-commerce system 100 may communicate with thepayment processing system 136 and the vendor order fulfillment system138 to execute the transactions.

The account management module 102 in the e-commerce system 100 maymanage data related to accounts for customers and vendors thatparticipate in commerce via the e-commerce system 100. The accountmanagement module 102 may be or include, for example, a web application.Vendors may interact with the account management module 102 via a webbrowser such as the web browser module 134 in the vendor client device130. As one example, a user of the vendor client device 130 may provideinformation to the account management module 102 such as: product andpricing information to be used for email advertisements to be sent tocustomers in email campaigns; email formatting information to be usedfor email advertisements to be sent to customers; financial informationrelated to bank accounts and/or other types of financial accounts (suchas e-Payment accounts such as PayPal accounts) that may be used toreceived payments from customers of the e-commerce system 100, such asaccount numbers and/or other identifying information; and/or otherinformation. Customers may register with the e-commerce system 100 byinteracting with the account management module 102 via a web browsersuch as a web browser module (not depicted) in the customer clientdevice 120. A user of the customer client device 120 may provideinformation to the account management module 102 via the web browsersuch as: an email address associated with the customer; financialinformation associated with the customer, such as a credit cardinformation (such as a credit card number and expiration date), and/orother information related to bank accounts and/or other types offinancial accounts (such as e-Payment accounts) that may be used to makepayments to vendors via the e-commerce system 100; shipping addressinformation; billing address information; preferences regarding whichvendors the customer would like to receive email advertisements from;and/or other information. The account management module 102 may, via thedatabase module 104, store information received from the customer clientdevice 120 and/or the vendor client device 130 in the e-commercedatabase 106. The account management module 102 may also add informationto the e-commerce database 106 when customers and vendors register withthe e-commerce system 100, such as customer identifiers, vendoridentifiers, and other identifying information.

The message processing module 110 (in conjunction with the emailinterface module 112) may generate and transmit advertisement emailmessages to customers that are registered with the e-commerce system100, such as the user of the customer client device 120. Theadvertisement email messages may be HyperText Markup Language (HTML)email messages, Rich Text Format (RTF) email messages, and/or may bedefined according to any other appropriate format. The advertisementemail messages may include Uniform Resource Identifiers (URIs) orhyperlinks that are defined according to the mailto URI scheme. Eachmailto URI or hyperlink may describe an email message that may begenerated by an email client module (such as the email client module122) when that URI or hyperlink is selected. The generated message mayinclude a number of parameters that indicate, for example, a productthat was advertised in the advertisement email that the customer wishesto purchase. The generated message may then be sent to the e-commercesystem 100, and received by the message processing module 110; when thegenerated message is received by the message processing module 110, themessage processing module 110 may then initiate a transaction topurchase the product indicated in the message on behalf of the customer.In such an instance, the message processing module 110 may interact withthe order execution module 108 to perform the transaction.

The email interface module 112 may be configured to use one or moreemail accounts that are associated with the e-commerce system 100, andto send and receive messages associated with the one or more emailaccounts. The email interface module 112 and/or the email client module122 in the customer client device 120 may communicate email messagesusing technologies such as Simple Mail Transfer Protocol (SMTP), PostOffice Protocol (POP) technology, Internet Message Access Protocol(IMAP), Remote Procedure Call (RPC) technology, HyperText TransferProtocol (HTTP), and/or other appropriate technologies. The interfacemodule 112 and/or the email client module 122 may use these technologiesto transmit and/or receive email messages via one or more email servers(not depicted). The email client module 122 may be or include an emailclient such as Microsoft Outlook, Thunderbird, a web browserapplication, or any other client application for the communication ofemail messages. In an instance where the email client module 122 is orincludes a web browser application, the email client module 122 may bethe same web browser described above that may be used to communicatewith the account management module 102; alternatively the email clientmodule 122 and the web browser described above that may be used tocommunicate with the account management module 102 may be different.

The payment processing system 136 may be, as one example, a paymentgateway that is operated by an acquiring financial institution. In aninstance where the payment processing system is a payment gateway, thepayment processing system 136 may have a connection to one or morebanking networks (not depicted) that it may use to process payments. Theorder execution module 108 may communicate with the payment processingsystem 136 using technology such as Transport Layer Security (TLS) orSecure Sockets Layer (SSL) technology. The vendor order fulfillmentsystem 138 may be an order management system (OMS), Enterprise ResourcePlanning (ERP), supply chain management, electronic purchasing system,inventory control system, or any other appropriate system for fulfillingorders.

The e-commerce database 106 may store information such as informationthat describes email campaigns, email advertisements that may be sent tocustomers, customer information, vendor information, productinformation, donation-related information, order status information,and/or other information. Further the e-commerce database 106 may storeinformation that indicates correspondences between different emailcampaigns, advertisements, customers, vendors, products, donations,information related to order statuses, and/or other information. Foreach email campaign, the e-commerce database 106 may store informationthat include an identifier of the vendor associated with the campaign,identifiers of the products associated with the campaign, and/or otherinformation. For each order that is placed with the e-commerce system100, the e-commerce database 106 may store information such as anidentifier of the customer that placed the order, when the order wasplaced, an identifier of the vendor associated with the order, and/orother information.

For each product described in the e-commerce database 106, thee-commerce database 106 may store information that includes anidentifier of the product (or donation), a description of the product, atitle of the product, an identifier of the vendor associated with theproduct, a cost of the product, and/or other information. According toone approach, data that describes donations may be handled within thee-commerce database in the primarily the same way as the data thatdescribes products. As one example, the e-commerce database 106 maystore information that indicates that a type of wine (e.g., “Wine One,”with a product identifier of “0005”) is sold by a vendor (e.g., “TheWine Shop,” with a vendor identifier of “0163”) for $15.00. Further, thee-commerce database may also store information that indicates that anexample vendor that is a non-profit organization (e.g., “CharitableOrganization,” with a vendor identifier of “1043”) may receive donationsfor $5.00, $10.00, $25.00, $50.00, and $100.00. Each of the differentdonation amounts may be stored in the e-commerce database 106 as adifferent product. For example, the $100 donation may have a productidentifier (or “donation identifier”) of “0099.” Further according tothis example, the e-commerce database 106 may store information thatindicates that the product with identifier “0099” indicates a donationof $100.00 to a vendor with the identifier of “1043.” Alternatively oradditionally, the e-commerce database 106 may store information (e.g.,one or more flags or other fields) that indicates, for eachproduct/donation, whether the product/donation relates to a donation orto a purchase of goods.

The e-commerce database 106 may be spread across one or any number ofcomputer-readable storage media (not depicted). The e-commerce database106 may be or include, for example, a relational database, ahierarchical database, an object-oriented database, a flat file, aspreadsheet, or a structured file. The database module 104 may interfacewith a database management system (not depicted) in order to add datato, modify data in, or obtain data from the e-commerce database 106.Alternatively or additionally, the database module 104 may performdatabase driver and/or database client functionality to interact withthe database management system. The database management system may bebased on a technology such as Microsoft SQL Server, Microsoft Access,MySQL, PostgreSQL, Oracle Relational Database Management System (RDBMS),Not Only SQL (NoSQL), or any other appropriate technology.

Each or any combination of the modules described above with reference toFIG. 1 (including the account management module 102, database module104, order execution module 108, message processing module 110, emailinterface module 112, email client module 122, web browser module 134,and the web browser module in the customer client device 120) may beimplemented as software modules, specific-purpose processor elements, oras combinations thereof. Suitable software modules include, by way ofexample, an executable program, a function, a method call, a procedure,a routine or sub-routine, one or more processor-executable instructions,an object, or a data structure. In addition or as an alternative to thefeatures of these modules described above with reference to FIG. 1 ,these modules may perform functionality described below with referenceto FIGS. 2A-13 .

FIGS. 2A-2B show an example method for email-based electronic commerce.FIGS. 2A-2B show components of the e-commerce system 100, including themessage processing module 110, the order execution module 108, and theemail interface module 112. FIGS. 2A-2B also show the email clientmodule 122 of the customer client device 120, as well as the paymentprocessing system 136 and the vendor order fulfillment system 138.

The method of FIGS. 2A-2B may begin with the message processing module110 determining that an advertising email message should be sent tocustomers of the e-commerce system 100 (step 240). This determinationmay be based on, for example, information provided by a user of thevendor client device 130 to account management module 102 in thee-commerce system 100 via the web browser module 134 in the vendorclient device 130. This information may include, for example, aninstruction that indicates that the advertising email message should besent. Alternatively or additionally, this information may includeinformation that defines an email campaign. Information that defines anemail campaign may include information that describes the format andcontents of the advertising email message. For example, the informationmay indicate the products that should be indicated in the advertisingemail message, the quantities in which they may be bought, prices forthe products, and/or other information. Alternatively or additionally,in an instance where the advertising message is a solicitation for adonation to a non-profit organization, this information may describeamounts of suggested donations. Information that defines the emailcampaign may also include parameters that define customers to whom theadvertising emails should be sent. For example, a campaign may bedefined such that the advertising emails will be sent only to users whohave not purchased an item from the vendor since a given time period.

The message processing module 110 and/or the email interface module 112may then generate the advertising email messages that are to betransmitted according to the information that describes the emailcampaign (step 242). This may include, for example, the messageprocessing module 110 obtaining information from the e-commerce database106 via the database module 104 that indicates a list of email addressesand other identifying information (such as customer identifiers) forcustomers that are the intended recipients of the email messages asdescribed in the email campaign information. The advertising emailmessages may indicate that they are being sent by one of the emailaccounts used by the e-commerce system 100. This may also include themessage processing module 110 assigning an email campaign identifierthat is associated with this email campaign.

Further, the email messages generated by the message processing module110 may include one or more mailto hyperlinks that define the contentsof email messages that are generated when the mailto hyperlinks areselected. For example, and as will be described in further detail below,the message processing module 110 may generate the contents of themailto hyperlinks such that the hyperlinks include information thatidentifies products that are being sold by a vendor. When the mailtohyperlinks are selected, new email messages are generated that may beused to initiate orders to purchase the identified products.

Mailto hyperlinks in the advertising email messages may include one orany combination of the following fields: a “mailto:” and/or “to” fieldthat indicate one or more email addresses of recipients of the newmessage; a “Copy To” or “CC” field that indicates one or more emailaddresses of recipients to whom a copy of the new message should besent; a “Blind Copy To” or “BCC” field that indicates one or more emailaddresses of recipients to whom a blind copy of the new message shouldbe sent; a field that indicates the subject of the new message; and afield that indicates the body of the new message. The mailto hyperlinksmay be defined according to the format described in Internet EngineeringTask Force (IETF) RFC2368, which is incorporated by reference as iffully set forth herein.

The email interface module 112 may then transmit one of the generatedadvertising email messages to the email client module 122 (step 244).The email message may be received by the email client module 122 anddisplayed by the email client module 122 (step 246).

Referring now to both FIG. 2A and FIG. 3 , FIG. 3 shows an email displaywindow 340 that may be used by the email client module 122 to display afirst example email message from the message processing module 110 (step246). The email display window 340 may include a Reply button 342, acontrol area 344, and a message body area 346. The control area 344 maydisplay control and/or header information associated with the emailmessage, such as the email addresses of the sender and recipient of themessage. According to this example, the control area 344 shows that thesender of the message has the email address “sales@company.com.” This isan email address that may be associated with an account used by thee-commerce system 100 for the communication of email messages. Furtherto this example, the control area 344 shows that the email address ofthe example recipient of the message (John Smith) is“john.smith@customer.com.” The control area 344 may also displayinformation such as a subject of the email message and the time theemail message was sent. The Reply button 342 may respond to user inputto generate a new display element (not depicted) to respond to the emailmessage.

The message body area 346 may display the body of the email message. Asshown in FIG. 3 , the message body area 346 may display an example emailmessage that shows information related to two example products (Wine Oneand Wine Two) that are being offered for sale by an example vendor (TheWine Shop). The message body area 346 includes a picture of a bottle ofeach type of wine, as well as the price for a bottle of each type ofwine. The message body area 346 also includes, under the picture of thebottle of Wine One, a number of mailto hyperlinks, such as the “1Bottle,” “2 Bottles,” “3 Bottles”, “6 Bottles,” and “1 Case (10%Discount)” links. The message body area 346 also includes similar linksunder the picture of the bottle of Wine Two. These links may be definedaccording to the mailto URI scheme or other appropriate format, and eachmay describe a new email message that may be generated by the emailclient module 122 when that link is selected.

The “1 Bottle” hyperlink beneath the picture of the Wine One bottle mayinclude information that describes an email message that, if received bythe e-commerce system 100, will indicate to the e-commerce system 100that John Smith would like to purchase one bottle of Wine One. As afurther example, Wine One may have a product identifier of “0005,” andJohn Smith may have a customer identifier of “0777.” According to thisexample, the “1 Bottle” hyperlink may describe an email message that isaddressed to an email account that is associated with the e-commercesystem 100, and that includes a message body that includes theidentifier for John Smith (“0777”), an identifier of the selectedproduct (“0005”), and an identifier of the quantity that John Smithwould like to order (in this example, a single bottle). Alternatively oradditionally, the email message described by the hyperlink may includeinformation such as text that describes the order, an identifier of thevendor (in this example, The Wine Shop), an email campaign identifier,and/or other information. Similarly, the “2 Bottles” hyperlink beneaththe picture of the Wine One bottle may include information thatdescribes an email message that, if received by the e-commerce system100, will indicate to the e-commerce system 100 that John Smith wouldlike to purchase two bottles of Wine One. According to this example, the“2 Bottles” hyperlink may be defined as follows:

<a href=“mailto:sales@company.com?subject=Purchase%20from%20Wine%20Shop%20&body=You%20have%20created%20an%20order%20for%20two%20bottles%20of%20Wine%20One.%20Press%20the%20Send%20button%20to%20complete%20the%20order.%0A%0AProductID0005%20QualifierNA%20Qty0002%20CustomerID0777%20CampaignID0003” target=“_blank”>2 Bottles</a>

Similarly, the “3 Bottles,” “6 Bottles,” and “1 Case (10% Discount)”hyperlinks beneath the picture of the Wine One bottle indicatecorresponding information for three bottles, six bottles, and one caseof bottles, respectively. Additionally, the “1 Bottle,” “2 Bottles,” “3Bottles,” “6 Bottles,” and “1 Case (10% Discount)” hyperlinks under theWine Two bottle indicate corresponding information for Wine Two as thatdescribed above with respect to the mailto hyperlinks relating to WineOne.

The email client module 122 may receive a user input that indicates thatone of the hyperlinks displayed in the message body area 346 isselected. The user input may be, for example, a mouse click, keyboardinput, or any other type of input that indicates that a hyperlink isselected. Referring again to FIG. 2A, the email client module 122 may,in response to this user input, generate and display an order emailmessage as specified by the selected hyperlink (step 248).

Referring now to FIG. 2A, FIG. 3 , and FIG. 4 , FIG. 4 shows an examplemessage composition window 440 that may be displayed in response to aselection of a hyperlink from the message body area 346 of the emaildisplay window 340 of FIG. 3 (step 248). The message composition window440 of FIG. 4 may include a Send button 442, a To area 450, a CC area452, a BCC area 454, a Subject area 456, and a message body area 446.The Send button 442 in the message composition window 440 of FIG. 4 maybe responsive to input from a user such as a mouse click, keyboardinput, or any other type of input. The different areas 446, 450, 452,454, 456 in the message composition window 440 display differentportions of an email message. For example, the To area 450 includes textthat indicates email addresses to which the email message is addressed,while the message body area 446 displays the contents of the body of theemail message. Each or any of these different areas 446, 450, 452, 454,456 may be editable based on user input. Changes to the contents ofthese areas 446, 450, 452, 454, 456 may change the corresponding portionof the email message.

FIG. 4 shows an example wherein the “2 Bottles” hyperlink beneath thepicture of the Wine One and described above with reference to FIG. 3 isselected. The To area 450 indicates that the message is addressed tosales@company.com. The Subject area 456 indicates that the subject ofthe message is “Purchase from Wine Shop.” The CC area 452 and BCC area454 are blank. Continuing the example of FIG. 3 , Wine One product has aproduct identifier of “0005” and John Smith has a customer identifier of“0777.” Accordingly, the message body area 446 includes the text“ProductID0005” and “CustomerID0777.” To indicate that the user hasselected the purchase of two bottles, the message body area 446 includesthe text “Qty0002.” Further, the message body area 446 includes the text“CampaignID0033,” indicating that the order is associated with an emailcampaign with an identifier of “0033.”

In an instance where a different hyperlink from the message body area346 of FIG. 3 is selected, the display areas 446, 450, 452, 454, 456 inthe message composition window 440 may include contents specified by theselected different hyperlink. For example, in an instance where ahyperlink related to Wine Two is selected, the message body area wouldnot include the text “ProductID0005,” but would include text thatindicates the corresponding identifier for Wine Two.

Referring now to both FIG. 2A and FIG. 5 , FIG. 5 shows an email displaywindow 540 that may be used by the email client module 122 to display asecond example email message from the message processing module 110(step 246). The email display window 540 includes a Reply button 542, acontrol area 544, and a message body area 546. These display elements542, 544, 546 may possess similar and/or analogous characteristicsand/or perform similar functionality as corresponding display elements342, 344, 346 in the email display window 340 of FIG. 3 . According tothe example of FIG. 5 , the control area 544 shows that the sender ofthe message has the email address “donate@company.com.” This is an emailaddress that may be associated with an account used by the e-commercesystem 100 for the communication of email messages. Further to thisexample, the control area 544 shows that the email address of theexample recipient of the message (John Smith) is“john.smith@customer.com.”

As shown in FIG. 5 , the message body area 546 of the email displaywindow 540 may display an example email message that shows informationrelated the solicitation of donations for an example non-profitorganization (“Charitable Organization”). The message body area 546 alsoincludes mailto hyperlinks, such as the “$5.00,” “$10.00,” “$25.00,”“$50.00,” and “$100.00” hyperlinks. These hyperlinks may possess similarand/or analogous characteristics, and/or include similar and/oranalogous information, as the mailto hyperlinks described above withreference to FIG. 3 . The “$5.00” hyperlink describes an email messagethat, if received by the e-commerce system 100, will indicate to thee-commerce system 100 that John Smith would like to donate $5.00 toCharitable Organization. Similarly, the “$10.00,” “$25.00,” “$50.00, and“$100.00” hyperlinks describe email messages with correspondinginformation for $10.00, $25.00, $50.00, and $100.00 donations,respectively.

The email client module 122 may receive a user input that indicates thatone of the hyperlinks displayed in the message body area 546 isselected. Referring again to FIG. 2A, the email client module 122 may,in response to this user input, generate and display an order emailmessage as specified by the selected hyperlink (step 248).

Referring now to FIG. 2A, FIG. 5 , and FIG. 6 , FIG. 6 shows an examplemessage composition window 640 that may be displayed in response to aselection of a hyperlink from the message body area 546 of the emaildisplay window 540 of FIG. 5 (step 248). The message composition window640 of FIG. 6 may include a Send button 642, a To area 650, a CC area652, a BCC area 654, a Subject area 656, and a message body area 646.These display elements 642, 650, 652, 654, 656, 646 may possess similarand/or analogous characteristics and/or perform similar functionality ascorresponding display elements 442, 450, 452, 454, 456, 446 in themessage composition window 440 of FIG. 4 .

FIG. 6 shows an example wherein the “$100.00” hyperlink from the messagebody area 546 of the email display window 540 of FIG. 5 is selected. TheTo area 650 indicates that the message is addressed todonate@company.com. The Subject area 656 indicates that the subject ofthe message is “Donation to Charitable Organization.” The CC area 652and BCC area 654 are blank. According to this example, a donation of$100.00 to Charitable Organization has a product identifier of “0099,”and John Smith has a customer identifier of “0777.” Accordingly, themessage body area 646 includes the text “ProductID0099” and“CustomerID0777.” Further, the message body area 646 includes the text“CampaignID0044,” indicating that the order is associated with an emailcampaign with an identifier of “0044.”

Referring again to FIG. 2A, the email client module 122 may send thegenerated order email message to the e-commerce system 100 (step 250).This may be performed in response to input from a user of the customerclient device 120. As one example, the email client module 122 may, inresponse to a selection of the Send button 442 in the messagecomposition window 440 of FIG. 6 , transmit an order email message basedon the contents of the fields 446, 450, 452, 454, 456 in the messagecomposition window 440. As another example, the email client module 122may, in response to a selection of the Send button 642 in the messagecomposition window 640 of FIG. 6 , transmit an order email message basedon the contents of the fields 646, 650, 652, 654, 656 in the messagecomposition window 640.

Referring now to FIG. 2B, the email interface module 112 and the messageprocessing module 110 may then receive the order email message (step252). This may include, for example, the message processing module 110periodically querying the email interface module 112 for informationrelated to new messages received by the email interface module 112 forone or more of the email accounts used by the e-commerce system 100.

Further, the message processing module 110 may validate the contents ofthe order email message by determining if the message is formattedcorrectly and/or includes information that it should include. Forexample, the message processing module 110 may be configured to expectthat the text of the body of the order email message should includeinformation related to an order placed by a customer, such as anidentifier of a customer that transmitted the message, a productidentifier, an identifier that indicates a donation amount, anidentifier of a vendor associated with the order, information thatindicates a quantity associated with the order, a campaign identifier,and/or other information. In an instance where the message processingmodule 110 determines that the information included in the order emailmessage is invalid (e.g., if one or more required pieces of informationare missing and/or formatted incorrectly), the message processing module110 may send one or more emails (not depicted) to the email address fromwhich the order email message was received, indicating that the orderemail message could not be correctly processed.

Alternatively or additionally, the message processing module 110 mayvalidate the contents of the order email message by determining whetherit includes information that matches data stored in the e-commercedatabase 106. For example, the message processing module 110 maydetermine whether one or more identifiers (such as a customeridentifier, product identifier, vendor identifier, or campaignidentifier) in the message corresponds to a valid identifier in thee-commerce database 106. In an instance where the message processingmodule 110 determines that the information included in the order emailmessage is invalid (e.g., if one or more of the identifiers in themessage are not valid identifiers), the message processing module 110may send one or more emails (not depicted) to the email address fromwhich the order email message was received, indicating that the orderemail message could not be correctly processed.

The message processing module 110 may then determine whether an orderconfirmation procedure should be performed (step 254). This may be basedon, for example, a parameter related to the vendor with which the ordercorresponding to the order email message is associated. For example, avendor might configure the e-commerce system 100 such that all ordersfor that vendor do or do not require an order confirmation before theorders are processed. This information may be provided to the accountmanagement module 102 in the e-commerce system 100 via, for example, theweb browser module 134 in the vendor client device 130. The accountmanagement module 102 may store this information in the e-commercedatabase 106. To perform this determination, the message processingmodule 110 may determine which vendor to which the order pertains, basedon a product identifier and/or vendor identifier include in the orderemail message. The message processing module 110 may then access thee-commerce database 106 via the database module 104 to determine whetherthis vendor has indicated whether an order confirmation is requiredbefore the order is processed.

Alternatively or additionally, the message processing module 110 maydetermine whether an order confirmation procedure should be performedbased on the nature of the order (step 254). For example, the messageprocessing module may be configured to determine that orders that do notrequire fulfillment of an order by a merchant (for example, orders thatrelate only to a donation or other pure exchange of funds) do notrequire an order confirmation procedure, while orders that relate torelate to the fulfillment of an order for tangible goods do require anorder confirmation procedure.

In an instance where the message processing module 110 determines thatan order confirmation procedure is required, the message processingmodule 110, email interface module 112, and the email client module 122may perform an order confirmation procedure (step 256).

As one example, the order confirmation procedure (step 256) may includethe transmission of one or more confirmation email messages (notdepicted in FIG. 2B) from the message processing module 110 to the emailclient module 122) that indicates that the order has been received.These confirmation email messages may be generated by the messageprocessing module 110, and transmitted to the email client module 122via the email interface module 112. One example of such a confirmationemail message is shown in FIG. 7 .

FIG. 7 shows an email display window 740 that may be used by the emailclient module 122 to display the example confirmation email messagereceived from the message processing module 110. The email displaywindow 740 includes a Reply button 742, a control area 744, and amessage body area 746. These display elements 742, 744, 746 may possesssimilar and/or analogous characteristics and/or perform similarfunctionality as corresponding display elements 342, 344, 346 in theemail display window 340 of FIG. 3 .

Alternatively or additionally, during the order confirmation procedure(step 256), the message processing module 110 (in conjunction with theemail interface module 112) may exchange one or more email messages withthe email client 122, in order to determine whether the order should becanceled, or whether the order should be executed. In such an instance,the message processing module 110 and/or the order execution module 108may determine, based on the exchange email messages, whether the ordershould be executed.

Alternatively or additionally, the order confirmation procedure (step256) may be or include the any or any combination of the actions shownin FIG. 8 , which is described in further detail below.

In an instance where the message processing module 110 and/or the orderexecution module 108 make a determination that the order should beexecuted, or in an instance where an order confirmation procedure is notperformed, and/or in any other appropriate context, an order executionprocedure may be performed, to complete the order indicated in the orderemail message (step 258). The message processing module 110, the orderexecution module 108, the payment processing module 136, and/or thevendor order fulfillment system 138 may participate in the orderexecution procedure (step 258).

The order execution procedure may include, for example, the orderexecution module 108 accessing credit card account and/or otherfinancial information related to the customer that is stored in thee-commerce database 106 via the database module 104. This may alsoinclude the order execution module accessing bank account and/or otherfinancial information related to the vendor that is stored in thee-commerce database 106 via the database module. The order executionmodule 108 may transmit the financial information related to both thecustomer and the vendor to the payment processing system 136, indicatingthat a payment should be made from the account of the customer to theaccount of the vendor.

Alternatively or additionally, an example order execution procedure mayinclude one or more of the following actions: The order execution module108 may access the order email message, which may include an identifierof the customer and a donation identifier/product identifier. Based onthe donation identifier, the order execution module 108 may determinethe non-profit organization to which the donation indicated in the orderemail message is intended. Further, the order execution module 108 maydetermine, based on the donation identifier, the amount to be donated.The order execution module 108 may determine the non-profit organizationto which the donation indicated in the order email message is intendedand the amount to be donated by, for example, querying the e-commercedatabase 106 (via the database module). Further, the order executionmodule 108 may perform a query of the e-commerce database 106 (via thedatabase module 104) to obtain financial information for the customerand the non-profit organization. The query to the e-commerce database106 for the customer's financial information may include the identifierof the customer, and the response to the query may be the customer'sfinancial information. Similarly, the query to the e-commerce database106 may include the identifier of the vendor, and the response to thequery may be the vendor's financial information The financialinformation for the customer may include, for example, credit cardinformation (such as a credit card number and expiration date), and/orother information related to a bank account and/or other type offinancial accounts (such as an e-Payment account). The financialinformation for the vendor may include information related to a bankaccount and/or other types of financial account (such as an e-Paymentaccount) held by the vendor. The order execution module 108 may transmitthe financial information related to both the customer and the vendor tothe payment processing system 136. As one example, the transmittedfinancial information may include an account number of the vendor andthe credit card number and expiration date for a credit card accountheld by the customer, and the transmitted financial information mayindicate that payment should be made to the to the identified account ofthe vendor from the credit card account of the customer for the amountindicated in the order email message.

Alternatively or additionally, the order execution procedure may includethe order execution module 108 sending one or more messages to thevendor order fulfillment system 138 related to the order. For example,the order execution module 108 may send one or more messages to thevendor order fulfillment system 138 that indicate information such asthe shipping address of the customer, an identifier of the items beingordered, a quantity of the items being ordered, and/or otherinformation. Additionally, the vendor order fulfillment system 138 maycommunicate one or more messages to the order execution module 108 thatindicate status updates with respect to fulfillment of the order. Forexample, the vendor order fulfillment system 138 may send one or moremessages to the order execution module 108 that indicate milestones inthe fulfillment of the order (e.g., that the goods involved in the orderhave shipped), and/or that fulfillment of the order is complete.

Alternatively or additionally, the order execution procedure may be orinclude any or any combination of the actions shown in FIG. 12 , whichis described in further detail below.

The message processing module 110 and/or the email interface module 112may then generate an order conclusion email message (step 260). Theorder conclusion email message may indicate, for example, that the orderwas successfully completed, whether an error occurred that preventedsuccessful completion of the order, that the order was canceled, and/orother information. The email interface module 112 may then transmit theorder conclusion email message to the email client 122 (step 262) in thecustomer client device 120. The email client 122 may then receive anddisplay the order conclusion email message (step 264). The email client122 may display the order conclusion email message in an email displaywindow (not depicted), with similar and/or analogous characteristics tothe email display window 740 described above with reference to FIG. 7 .

FIG. 8 shows an example order confirmation method that may be used withthe method of FIGS. 2A-2B, or in any other appropriate context. FIG. 8shows components of the e-commerce system 100, including the messageprocessing module 110, the order execution module 108, and the emailinterface module 112. FIG. 8 also shows the email client module 122 ofthe customer client device 120.

The method of FIG. 8 may begin with the message processing module 110and/or the email interface module 112 generating a confirmation emailmessage (step 840). The confirmation email message may includeinformation that indicates that an order has been placed, and may invitethe user of the email client module 122 to provide input as to whetherthe order should be completed or not. As will be described in furtherdetail below, the confirmation email message may include one or moremailto hyperlinks that describe a confirmation response email messagethat indicates whether the order should be completed or not.

Generating the confirmation email message (step 840) may also includedetermining the email address to which the confirmation email messageshould be sent. As described above with reference to FIG. 1 , thee-commerce database 106 may store information that includes a customeridentifier and an email address for each customer. According to a firstapproach for determining the email address to which the confirmationemail message should be sent, the message processing module 110 maydetermine the customer identifier associated with the order that isbeing confirmed. The message processing module may then obtain from thee-commerce database 106 (via the database module 104) the email addressthat is stored in the database that is associated with the customeridentifier. According to this approach, the message processing module110 may generate the confirmation email message such that it isaddressed to the email address that is stored in the database that isassociated with the customer identifier. According to this approach, itis possible that the email address from which the order email messagewas originally sent (as one example, as described above with respect tostep 250 of FIG. 2A) will be different from the address to which theconfirmation email message is sent. According to a second approach, themessage processing module 110 may generate the confirmation emailmessage, such that it is addressed to the same email address from whichthe order email message was originally sent.

The email interface module 112 may transmit the confirmation emailmessage to the email client module 122 (step 842). The confirmationemail message may be received by the email client module 122, anddisplayed by the email client module 122 (step 844).

Referring now to both FIG. 8 and FIG. 9 , FIG. 9 shows an email displaywindow 940 that may be used by the email client module 122 to display anexample confirmation email message (step 844). The email display window940 includes a Reply button 942, a control area 944, and a message bodyarea 946. These display elements 942, 944, 946 may possess similarand/or analogous characteristics and/or perform similar functionality ascorresponding display elements 342, 344, 346 in the email display window340 of FIG. 3 . According to the example of FIG. 9 , the control area944 shows that the sender of the message has the email address“sales@company.com.” This is an email address that may be associatedwith an account used by the e-commerce system 100 for the communicationof email messages. Further to this example, the control area 944 showsthat the email address of the recipient of the message (John Smith) is“john.smith@customer.com.”

As shown in FIG. 9 , the message body area 946 may include informationthat describes the order that is being confirmed. The message body areaalso includes mailto hyperlinks, such as the “Confirm Order” and “CancelOrder” links. The “Confirm Order” hyperlink describes an email messagethat, if received by the e-commerce system 100, will indicate to thee-commerce system 100 that John Smith would like to proceed with theorder indicated by the example confirmation email message. The “CancelOrder” hyperlink describes an email message that, if received by thee-commerce system 100, will indicate to the e-commerce system 100 thatJohn Smith would like to cancel the order indicated by the exampleconfirmation email message.

The email client module 122 may receive a user input that indicates thatone of the hyperlinks displayed in the message body area 946 isselected. The user input may be, for example, a mouse click, keyboardinput, or any other type of input that indicates that a hyperlink isselected. Referring again to FIG. 8 , the email client module 122 may,in response to this user input, generate and display a confirmationresponse email message as specified by the selected hyperlink (step846).

Referring now to FIG. 8 , FIG. 9 , and FIG. 10 , FIG. 10 shows anexample message composition window 1040 that may be displayed inresponse to a selection of the “Confirm Order” hyperlink from themessage body area 946 of the email display window 940 of FIG. 9 (step846). The message composition window 1040 of FIG. 10 may include a Sendbutton 1042, a To area 1050, a CC area 1052, a BCC area 1054, a Subjectarea 1056, and a message body area 1046. These display elements 1042,1050, 1052, 1054, 1056, 1046 may possess similar and/or analogouscharacteristics and/or perform similar functionality as correspondingdisplay elements 442, 450, 452, 454, 456, 446 in the message compositionwindow 440 of FIG. 4 .

Referring now to FIG. 8 , FIG. 9 , and FIG. 11 , FIG. 11 shows anexample message composition window 1140 that may be displayed inresponse to a selection of the “Cancel Order” hyperlink from the messagebody area 946 of the email display window 940 of FIG. 9 (step 846). Themessage composition window 1140 of FIG. 11 may include a Send button1142, a To area 1150, a CC area 1152, a BCC area 1154, a Subject area1156, and a message body area 1146. These display elements 1142, 1150,1152, 1154, 1156, 1146 may possess similar and/or analogouscharacteristics and/or perform similar functionality as correspondingdisplay elements 442, 450, 452, 454, 456, 446 in the message compositionwindow 440 of FIG. 4 .

Referring again to FIG. 8 , the email client module 122 may send thegenerated confirmation response email message to the e-commerce system100 (step 848). This may be performed in response to input from a userof the customer client device 120. As one example, the email clientmodule 122 may, in response to a selection of the Send button 1042 inthe message composition window 1040 of FIG. 11 , transmit the emailmessage based on the contents of the fields 1046, 1050, 1052, 1054, 1056in the message composition window 1040. As another example, the emailclient module 122 may, in response to a selection of the Send button1142 in the message composition window 1140 of FIG. 11 , transmit theemail message based on the contents of the fields 1146, 1150, 1152,1154, 1156 in the message composition window 1140.

The email interface module 112 and the message processing module 110 maythen receive the confirmation response email message (step 850). Thismay include, for example, the message processing module 110 periodicallyquerying the email interface module 112 for information related to newmessages received by the email interface module 112 for one or more ofthe email accounts used by the e-commerce system 100.

Further, the message processing module 110 may validate the contents ofthe confirmation response email message by determining if the message isformatted correctly and/or includes information that it should include.For example, the message processing module 110 may be configured toexpect that the text of the confirmation response email message shouldinclude information that indicates an identifier of an order to whichthe confirmation response email message pertains. Alternatively oradditionally, the message processing module 110 may validate thecontents of the order email message by determining whether it includesinformation that matches data stored in the e-commerce database 106. Forexample, the message processing module 110 may determine whether anorder identifier in the confirmation response email message correspondsto a valid order identifier. In an instance where the message processingmodule 110 determines that the information included in the order emailmessage is invalid (e.g., if an order identifier in the message is not avalid order identifier), the message processing module 110 may send oneor more emails (not depicted) to the email address from which theconfirmation response email message was received, indicating that theconfirmation response email message could not be correctly processed.

The message processing module 110 and/or the order execution module 108may then determine whether the order should be executed (step 852). Thismay be based on, for example, the contents of the confirmation responseemail message. In an instance where the confirmation response emailmessage indicates that the order should be canceled, the messageprocessing module 110 and/or the order execution module 108 maydetermine that the order should be canceled. In an instance where theconfirmation response email message indicates that the order should beexecuted, the message processing module 110 and/or the order executionmodule 108 may determine that the order should be executed.

FIG. 12 shows an example order execution method that may be used inconjunction with the method of FIGS. 2A-2B, or in any other appropriatecontext. FIG. 12 shows the order execution module 108 and the databasemodule 104 of the e-commerce system 100, as well as the paymentprocessing system 136 and the vendor order fulfillment system 138.

The method of FIG. 12 may begin with the order execution module 108obtaining credit card information associated with the customer for whomthe order will be executed (step 1240). This may include the obtainingthe credit card information from the e-commerce database 106 via thedatabase module 104. The credit card information may include a creditcard number and an expiration date.

The order execution module 108 may then communicate with the paymentprocessing module 136 to put a preauthorization hold on the customer'saccount for the amount required for the order (step 1242). This mayinclude, for example, the order execution module 108 sending one or moremessages to the payment processing system 136 that include the creditcard information and the amount that should be held. This may alsoinclude the payment processing system 136 sending one or more messagesto the order execution module 108 that indicate that the hold wassuccessfully placed on the customer's account.

The order execution module 108 and the payment processing module 136 maythen communicate to fulfill the order (step 1244). This may include, forexample, the order execution module 108 sending one or more messages tothe vendor order fulfillment system 138 that include information such asthe shipping address of the customer, an identifier of the items beingordered, a quantity of the items being ordered, and/or otherinformation. This may also include the vendor order fulfillment system138 sending one or more messages to the order execution module 108 thatindicate status updates with respect to fulfillment of the order. Forexample, the vendor order fulfillment system 138 may send one or moremessages to the order execution module 108 that indicate progress withrespect to the fulfillment of the order, and/or that fulfillment of theorder is complete.

The order execution module 108 may then communicate with the paymentprocessing system 136 to charge the customer's account for the amountassociated with the order (step 1246). This may include the orderexecution module 108 sending one or more messages to the paymentprocessing system that indicate that the customer's account should becharged for the amount associated with the order. This may also includethe payment processing system 136 sending one or more messages to theorder execution module 108 that indicate that the customer's account wassuccessfully charged. Charging the customer's account (step 1246) maybeperformed in response to the order execution module 108 receivinginformation from the vendor order fulfillment system 138 that indicatesthat the order has been completed. Alternatively, the order executionmodule 108 may determine that, if a preconfigured amount of time (e.g.,forty-eight hours) has passed since an order had been first communicatedto the order fulfillment system 138 (step 1244) and no error orcancellation messages had been received by the order execution module108 from the order fulfillment system 138, the order had beensuccessfully fulfilled and that the customer's account should becharged. The order execution module 1246 may then communicate with thepayment processing system 136 to charge the customer's account inresponse to this determination. Alternatively or additionally, a vendormay communicate with the account management module 102 in the e-commercesystem 100 to provide information via a web interface that indicatesthat an order has been fulfilled. In such an instance, the accountmanagement module 102 may store information in the e-commerce database106 that indicates that the order has been fulfilled. The orderexecution module 108 may periodically obtain data from the e-commercedatabase via the database module 104 that reflects whether the order hasbeen fulfilled. If the order execution module 108 obtains informationthat indicates that the order has been fulfilled, the order executionmodule 108 may determine that the customer's account should be charged;the order execution module 1246 may then communicate with the paymentprocessing system 136 to charge the customer's account in response tothis determination.

FIG. 13 shows an example system 1300 that may be used to implementfeatures described above with respect to FIGS. 1-12 . The example system1300 includes an e-commerce server 1350, a client device 1370, and oneor more networks 1380.

The e-commerce server 1350 may include at least one processor 1352,memory device 1354, network interface 1356, and storage device 1358. Theclient device 1370 may include at least one processor 1372, memorydevice 1374, network interface 1376, input device interface 1375,display device interface 1377, and storage device 1378.

The e-commerce server 1350 may be configured to perform any feature orcombination of features described above with reference to FIGS. 1-12 asperformed by the account management module 102, database module 104,order execution module 108, message processing module 110, and/or emailinterface module 112. The client device 1370 may be configured toperform any feature or combination of features described above withreference to FIGS. 1-12 as performed by the email client module 122and/or the web browser module in the customer client device 120. Theclient device 1370 may be, for example, a desktop computer, a laptopcomputer, a netbook, a tablet computer, a personal digital assistant(PDA), a cellular phone, or any other appropriate device.

Each or any of the memory devices 1354, 1374 may be or include a devicesuch as a Dynamic Random Access Memory (D-RAM), Static RAM (S-RAM), orother RAM or a flash memory. Each or any of the storage devices 1358,1378 may be or include a hard disk, a magneto-optical medium, an opticalmedium such as a CD-ROM, a digital versatile disk (DVDs), or Blu-Raydisc (BD), or other type of device for electronic data storage. Thestorage device 1358 in the e-commerce server 1350 may store theinformation or any subset of the information described above withreference to FIGS. 1-12 as stored in the e-commerce database 106.

Each or any of the network interfaces 1356, 1376 may be, for example, acommunications port, a wired transceiver, or a wireless transceiver.Each or any of the network interfaces 1356, 1376 may be capable ofcommunicating using technologies such as Ethernet, fiber optics,microwave, xDSL (Digital Subscriber Line), Wireless Local Area Network(WLAN) technology, wireless cellular technology, and/or any otherappropriate technology. The network interfaces 1356, 1376 may be used bythe e-commerce server 1350 and/or the client device 1370 to communicatevia the one or more networks 1380. The network interface in thee-commerce server 1350 may be configured to communicate any of themessages and/or other information described above with reference toFIGS. 1-12 as communicated by the account management module 102,database module 104, order execution module 108, message processingmodule 110, and/or email interface module 112. The network interface1376 in the client device 1370 may be configured to communicate any ofthe messages and/or other information described above with reference toFIGS. 1-12 as communicated by the email client module 122 and/or by theweb browser module in the customer client device 120 used forcommunicating with the account management module 102.

The one or more networks 1380 may include one or more private networksand/or one or more public networks such as the Internet. The one or morenetworks 1380 may be based on wired and/or wireless networkingtechnologies.

The input device interface 1375 in the client device 1370 may be aninterface configured to receive input from an input device such as akeyboard, a mouse, a trackball, a scanner, a touch screen, a touch pad,a stylus pad, and/or other device. The input device interface 1375 mayoperate using a technology such as Universal Serial Bus (USB), PS/2,Bluetooth, infrared, and/or other appropriate technology. The inputdevice interface 1375 may be configured to receive any or anycombination of the user input described above with reference to FIGS.1-12 as received by the by the email client module 122 and/or by the webbrowser module in the customer client device 120 used for communicatingwith the account management module 102.

The display device interface 1377 may be an interface configured tocommunicate data to a display device (not depicted). The display deviceinterface 1377 may operate using technology such as Video Graphics Array(VGA), Super VGA (S-VGA), Digital Visual Interface (DVI),High-Definition Multimedia Interface (HDMI), or other appropriatetechnology. The client device 1370 may include or be connected to adisplay device (not depicted) via the display device interface 1377. Thedisplay device may be, for example, a monitor or television display, aplasma display, a liquid crystal display (LCD), and/or a display basedon a technology such as front or rear projection, light emitting diodes(LEDs), organic light-emitting diodes (OLEDs), or Digital LightProcessing (DLP). The display device may be configured to display, basedon data received via the display device interface 1377, any displayelements described above with reference to FIGS. 1-12 as displayed bythe email client module 122 and/or by the web browser module in thecustomer client device.

The memory device 1354 and/or the storage device 1358 of the e-commerceserver 1350 may store instructions which, when executed by the at leastone processor 1352, cause the at least one processor 1352 to perform anyfeature or combination of features described above with reference toFIGS. 1-12 as performed by the account management module 102, databasemodule 104, order execution module 108, message processing module 110,and/or email interface module 112. The memory device 1374 and/or thestorage device 1358 of the client device 1370 may store instructionswhich, when executed by the at least one processor 1372, cause the atleast one processor 1372 to perform any feature or combination offeatures described above with reference to FIGS. 1-12 as performed bythe email client module 122 and/or by the web browser module in thecustomer client device 120 used for communicating with the accountmanagement module 102.

Although FIG. 13 shows a single e-commerce server 1350 and a singleclient device 1370, the functionality described above with reference toFIG. 13 as performed by the e-commerce serve 1350 and/or the clientdevice 1370 may be distributed across any number of devices thatpossesses similar characteristics and/or that include similar components1352, 1354, 1356, 1358, 1372, 1374, 11375, 1376, 1377 as the e-commerceserver 1350 and/or the client device 1370.

While examples are provided above with respect to FIGS. 1-13 whichincludes the use of email communications, the features described abovewith respect to FIGS. 1-13 may also be implemented using different typesof communications technology. For example, the features described abovewith reference to FIGS. 1-13 may also be implemented, mutatis mutandis,using technologies that include any one or any combination of: email;instant messaging; enterprise messaging; Short Message Service (SMS);Multimedia Messaging Service (MMS); and/or any other appropriatetechnology for the electronic communication of data.

As use herein, the term “vendor” broadly refers to and is not limited toa business, a non-profit organization, any other type of organization,and/or an individual person. One example of a business is an onlineretailer. Examples of non-profit organizations include charitableorganizations, educational institutions such as schools anduniversities, arts organizations, and recreational organizations.Examples of recreational organizations include historical orpreservation societies, local recreational sports leagues.

As used herein, the term “processor” broadly refers to and is notlimited to a single- or multi-core general purpose processor, a specialpurpose processor, a conventional processor, a digital signal processor(DSP), a plurality of microprocessors, one or more microprocessors inassociation with a DSP core, a controller, a microcontroller, one ormore Application Specific Integrated Circuits (ASICs), one or more FieldProgrammable Gate Array (FPGA) circuits, any other type of integratedcircuit (IC), a system-on-a-chip (SOC), and/or a state machine.

As used to herein, the term “computer-readable storage medium” broadlyrefers to and is not limited to a register, a cache memory, a ROM, asemiconductor memory device (such as a D-RAM, S-RAM, or other RAM), amagnetic medium such as a flash memory, a hard disk, a magneto-opticalmedium, an optical medium such as a CD-ROM, a DVDs, or BD, or other typeof device for electronic data storage.

Although features and elements are described above in particularcombinations, each feature or element can be used alone or in anycombination with or without the other features and elements. Forexample, each feature or element as described above with reference to1-13 may be used alone without the other features and elements or invarious combinations with or without other features and elements.Sub-elements of the methods and features described above with referenceto FIG. 1-13 may be performed in any arbitrary order (includingconcurrently), in any combination or sub-combination.

What is claimed is:
 1. A method for facilitating an e-commercetransaction by using Simple Mail Transfer Protocol (SMTP) to improvesecurity of an e-commerce system, the method comprising: generating, bythe e-commerce system, a first message, the first message including afirst a plurality of visible SMTP mailto link and a second mailto linklinks that are each associated with a respective non-visible indicia andvisible indicia, each non-visible indicia including an SMTP emailaddress of an email account of the system and a respective one of aplurality of transaction identifiers, and each visible indiciacorresponding to a particular transaction identifier from the pluralityof transaction identifiers, wherein each link causes the generation ofthat when activated generates an SMTP email message addressed to anemail account of the e-commerce system, wherein the SMTP email messageincludes and including a corresponding particular transaction identifierand indication of whether the first mailto link or the second mailtolink was activated; transmitting, by the e-commerce system, the firstmessage to a user; receiving, by the e-commerce system, the SMTP emailmessage from an email address of the user via SMTP, wherein the SMTPemail message is generated in response to activation of either the firstmailto link or the second mailto link; to a selection of one of theplurality of visible SMTP mailto links and is addressed to the emailaddress of the e-commerce system, the SMTP email message including theparticular transaction identifier from the one of said visible SMTPmailto links that is selected, and performing, by the e-commerce system,a validation procedure based on the received SMTP email messagereceived, the validation procedure comprising comparing the particulartransaction identifier of the SMTP email message against informationstored in a database to confirm the e-commerce transaction should beexecuted; determining, by the e-commerce system, whether the firstmailto link was activated or the second mailto link was activated basedon the indication; and selectively executing, by the e-commerce system,the e-commerce transaction when the validation procedure indicates thetransaction identifier is valid, wherein the e-commerce transaction isexecuted when the first mailto link is activated and canceled when thesecond mailto link is activated.
 2. The method of claim 1, wherein theexecuting the e-commerce transaction includes further comprising:performing a transaction execution procedure including transmitting oneor more payment messages to a payment processing system.
 3. The methodof claim 2 further comprising: storing, by the e-commerce system in thedatabase, financial account information of the user in the database,wherein the one or more payment messages include the financial accountinformation of the user, and wherein the payment processing system is apayment gateway that is operated by an acquiring financial institution.4. A system for facilitating an e-commerce transaction by using SimpleMail Transfer Protocol (SMTP) to improve security of an e-commercenetwork, the system comprising: a communication interface that iscommunicatively coupled to a device of a user via the e-commercenetwork; a memory; and a processor communicatively coupled to thecommunication interface and the memory, wherein the processor isconfigured to; generate a first message, the first message including afirst a plurality of visible SMTP mailto link and a second mailto linklinks that are each associated with a respective non-visible indicia andvisible indicia, each non-visible indicia including an SMTP emailaddress of an email account of the system and a respective one of aplurality of transaction identifiers, and each visible indiciacorresponding to a particular transaction identifier from the pluralityof transaction identifiers, wherein each link causes the generation ofthat when activated generates an SMTP email message addressed to anemail account of the system, wherein the SMTP email message includes andincluding a corresponding particular transaction identifier andindication of whether the first mailto link or the second mailto linkwas activated; transmit, using the communication interface, the firstmessage to the user; receive, using the communication interface, theSMTP email message from an email address of the user via SMTP, whereinthe SMTP email message is generated in response to activation of eitherthe first mailto link or the second mailto link; to a selection of oneof the plurality of visible SMTP mailto links and is addressed to theemail address of the e-commerce system, the SMTP email message includingthe particular transaction identifier from the one of said visible SMTPmailto links that is selected, and perform a validation procedure basedon the received SMTP email message received, the validation procedurecomprising comparing the particular transaction identifier of the SMTPemail message against information stored in a database to confirm thee-commerce transaction should be executed; determine whether the firstmailto link was activated or the second mailto link was activated basedon the indication; and selectively execute the e-commerce transactionwhen the validation procedure indicates the transaction identifier isvalid, wherein the e-commerce transaction is executed when the firstmailto link is activated and canceled when the second mailto link isactivated.
 5. The system of claim 4, wherein the e-commerce transactionis executed by the processor is further configured to: perform atransaction execution procedure that includes transmitting, using thecommunication interface, one or more payment messages to a paymentprocessing system.
 6. The system of claim 5, wherein the processor isfurther configured to: store, in the database, financial accountinformation of the user in the database, wherein the one or more paymentmessages include the financial account information of the user, andwherein the payment processing system is a payment gateway that isoperated by an acquiring financial institution.
 7. A non-transitorycomputer readable storage medium having processor-executableinstructions stored thereon that when executed by a processor of ane-commerce system cause the processor to execute a method forfacilitating an e-commerce transaction by using Simple Mail TransferProtocol (SMTP) to improve security of an e-commerce network, the methodcomprising: generate generating, by the processor, a first message, thefirst message including a first a plurality of visible SMTP mailto linkand a second mailto link links that are each associated with arespective non-visible indicia and visible indicia, each non-visibleindicia including an SMTP email address of an email account of thesystem and a respective one of a plurality of transaction identifiers,and each visible indicia corresponding to a particular transactionidentifier from the plurality of transaction identifiers, wherein eachlink causes the generation of that when activated generates an SMTPemail message addressed to an email account of the e-commerce system,wherein the SMTP email message includes and including a correspondingparticular transaction identifier and indication of whether the firstmailto link or the second mailto link was activated; transmittransmitting, using a communication interface that is communicativelycoupled to the processor, the first message to a user; receiving,receive, using the communication interface, the SMTP email message froman email address of the user via SMTP, wherein the SMTP email message isgenerated in response to activation of either the first mailto link orthe second mailto link; to a selection of one of the plurality ofvisible SMTP mailto links and is addressed to the email address of thee-commerce system, the SMTP email message including the particulartransaction identifier from the one of said visible SMTP mailto linksthat is selected, and perform performing a validation procedure based onthe received SMTP email message received, the validation procedurecomprising comparing the particular transaction identifier of the SMTPemail message against information stored in a database to confirm thee-commerce transaction should be executed; determining whether the firstmailto link was activated or the second mailto link was activated basedon the indication; and selectively executing the e-commerce transactionwhen the validation procedure indicates the transaction identifier isvalid, wherein the e-commerce transaction is executed when the firstmailto link is activated and canceled when the second mailto link isactivated.
 8. The method of claim 1, wherein the first message istransmitted via Short Message Service (SMS) or Multimedia MessagingService (MMS).
 9. The method of claim 1, wherein the first message istransmitted via SMTP.
 10. The method of claim 1, further comprising:canceling, by the e-commerce system, the e-commerce transaction when theSMTP email message is not received within a predetermined amount of timefrom the transmitting the first message.
 11. The system of claim 4,wherein the first message is transmitted via Short Message Service (SMS)or Multimedia Messaging Service (MMS).
 12. The system of claim 4,wherein the first message is transmitted via SMTP.
 13. The system ofclaim 4, wherein the processor is further configured to: cancel thee-commerce transaction when the SMTP email message is not receivedwithin a predetermined amount of time from when the first message istransmitted.
 14. The non-transitory computer readable storage medium ofclaim 7, wherein the executing the e-commerce transaction includes:transmitting one or more payment messages to a payment processingsystem.
 15. The non-transitory computer readable storage medium of claim14, further comprising: storing financial account information of theuser in the database, wherein the one or more payment messages includethe financial account information of the user, and wherein the paymentprocessing system is a payment gateway that is operated by an acquiringfinancial institution.
 16. The non-transitory computer readable storagemedium of claim 7, wherein the first message is transmitted via ShortMessage Service (SMS) or Multimedia Messaging Service (MMS).
 17. Thenon-transitory computer readable storage medium of claim 7, wherein thefirst message is transmitted via SMTP.
 18. The non-transitory computerreadable storage medium of claim 7, wherein the method further includes:canceling, by the e-commerce system, the e-commerce transaction when theSMTP email message is not received within a predetermined amount of timefrom the transmitting the first message.